bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Fri, 20 Dec 2019 18:30:29 +0000 (18:30 +0000)
committerJames Clarke <jrtc27@debian.org>
Fri, 20 Dec 2019 18:30:29 +0000 (18:30 +0000)
commit6183a9fecab314a41ffc48ea12a90a6c91050e24
tree15070a56ba89caf8dd1d58875f3d8ea0ec3c154e
parent92e79bee3209f7b17104666a00dc42884c95a626
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h